home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
hardware
/
ep9301.exe
/
README.DOC
< prev
Wrap
Text File
|
1993-01-09
|
42KB
|
1,067 lines
ENET P-SERIES ETHERNET NETWORK ADAPTERS Jan 11, 1993
(930111)
┌───────────────────────────────────────────────────┐
│ │
│ DIRECTORY STRUCTURE │
│ │
└───────────────────────────────────────────────────┘
1) INTRODUCTION
This diskette provides different network device drivers in
order to let our network adapters work in different networking
environment. The configuration and diagnostic utilities included
are for configuring and testing the hardware of the adapters. All
files are arranged in the following directories.
a) <Root>
It contains NetWare IPX workstation and server
drivers. Two configuration information files (.LAN)
are found here for generating IPX server and
workstation drivers. The files used for Windows for
Workgroups can also be found here.
b) <Root>\DOSODI
NetWare ODI workstation driver can be found.
NET.CFG is a sample configuration file for your quick
reference.
c) <Root>\NETWARE.386
Users can find NetWare ODI server driver.
d) <Root>\MSLANMAN.DOS
This directory is used for installing DOS NDIS
driver in Microsoft LAN Manager. Please refer to the
section, LAN MANAGER, in this document for more
details.
e) <Root>\MSLANMAN.OS2
The driver for installation of OS/2 workstation
or OS/2 server can be found here. Please refer to the
section, LAN MANAGER, in the document for more
details.
f) <Root>\UTILITY
There are configuration and diagnostic utilities.
The document file, HELP.DOC provides some guidelines
for both utilities.
g) <Root>\PKT
There is a Packet Driver for our network adapters.
┌───────────────────────────────────────────────────┐
│ │
│ HISTORY OF DRIVERS AND UTILITIES │
│ │
└───────────────────────────────────────────────────┘
1) INTRODUCTION
This section records all modifications made on different
versions of device drivers and utilities.
1.1) ODI Server Driver
A) ENET386.LAN v2.10
a) This copy was modified from v2.02 and was
enhanced to support our P-series network adapters. It
can also support both M and U series network adapters.
1.2) ODI Workstation Driver
A) ENETCPSH.COM v1.30
a) This copy was modified from v1.22 and was
enhanced to support our P-series network adapters. It
can also support both M and U series network adapters.
1.3) IPX Server Drivers
A) ?ENETCP.OBJ v2.30
a) This copy was modified from v2.22 and was
enhanced to support our P-series network adapters. It
can also support both M and U series network adapters.
1.4) IPX Workstation Driver
A) ENETCPSH.OBJ v2.30
a) This copy was modified from v2.22 and was
enhanced to support our P-series network adapters. It
can also support both M and U series network adapters.
1.5) DOS NDIS Driver
A) ENET.DOS v2.30
a) This copy was modified from v2.00 and was
enhanced to support our P-series and ENET16-MC/P
network adapters. It can also support both M and U
series network adapters.
b) The driver was modified to support the full range
of I/O base address from 0x200 to 0x3e0.
c) After compiling for x88 processor, DOS NDIS driver
can run in XT machine.
d) After adding the codes to support more primitives
specified in the NDI specification v2.0.1, the driver can
work in DEC Pathworks for DOS.
1.6) OS/2 NDIS Driver
A) ENET.OS2 v2.30
a) This copy was modified from v2.00 and was
enhanced to support our P-series and ENET16-MC/P
network adapters. It can also support both M and U
series network adapters.
b) The driver was modified to support the full range
of I/O base address from 0x200 to 0x3e0.
c) Extra codes were added to support more primitives
in the NDI specification.
1.7) Packet Driver
A) ENETPKT.COM v1.00
a) This is our first release of Packet driver. It can
support our M, U and P series network adapters.
1.8) Configuration and Diagnostic Utilities
A) ENETUTIL.EXE v3.00
a) This copy was modified from ENETDIAG.EXE v2.10. We
did a lot of modifications in order to support P-series
network adapters. Please refer to the document, HELP.DOC
(which can be found in <Root>\UTILITY) for more
information.
┌───────────────────────────────────────────────────┐
│ │
│ LAN DRIVER CONFIGURATION PARAMETERS │
│ │
└───────────────────────────────────────────────────┘
IMPORTANT:
:- Please read this section before reading the driver
configuration parameters in other sections.
1) INTRODUCTION
All drivers included in this driver diskette can support all
ENET M, U and P series network adapters (for ISA). In order to
make use the software programmable capability in our P-series
network adapters, several new configuration parameters have been
added in the drivers. This section is intended to give users some
guidelines to make use some general configuration parameters to
configure the drivers. Users can refer to further information on
these parameters for different drivers in next sections.
2) CONFIGURATION PARAMETERS
Normally, the configuration parameters can be divided into
two different groups.
2.1) Basic Configuration Parameters
This group of parameters can be used for our M, U and P
series network adapters. They include I/O base address, IRQ
number and RAM base address. Users can follow the procedures
listed below to configure the drivers using these parameters.
a) Use jumpers to set the ENET M or U series network
adapter to correct I/O base address and IRQ number. For P-
series network adapter, users can use our configuration
utility to software configure it.
b) Configure the driver. Select correct I/O base address,
IRQ number and correct RAM base address in the driver. They
will be used to initialize the network adapter.
NOTE:
:- If one of the parameters is entered incorrectly, the
driver MAY not work properly.
2.2) Advanced Configuration Parameters
These parameters are VALID for P-series network adapters
ONLY. The drivers will prompt you errors if you use them with M
or U series network adapters. There are two advanced
configuration parameters: Mode and Physical Media.
a) Physical Media
Users can use this parameter to change the physical
media to whatever they want. The drivers will program the
storage device (EEPROM) on the P-series adapter and change
the physical media to that specified by this parameter.
Normally, if this parameters is NOT defined, the drivers
will use the preset physical media stored in the storage
device (EEPROM) on the network adapter.
NOTE:
:- Different types of network adapters can support
different types of physical media. Please refer to your
manual for further information.
:- The drivers DO NOT change the physical media
PERMANENTLY. Once users hardware-reset the workstation, the
physical media will be changed to the original setting that
is stored in the storage device (EEPROM).
b) Mode
For a P-series adapter, a driver can support two
different configuration modes: AUTO and PROGRAM.
If a driver is configured to AUTO (Automatic
Configuration Mode), it will ignore THREE basic
configuration parameters: I/O base address, IRQ number and
RAM base address. It will search all valid I/O base address
and initializes the FIRST P-series network adapter in your
workstation. Then it READS the hardware settings, IRQ
number and RAM base address, from the storage device
(EEPROM) on the network adapter.
If a driver is configured to PROGRAM (Program
Configuration Mode), it will interpret the meaning of THREE
basic configuration parameters differently. The driver will
search all valid I/O base address and initialize the FIRST
P-series network adapter. And then it will change the I/O
base address, IRQ number and RAM base address to that
specified by THREE basic configuration parameters. So the
network adapter will use the hardware settings specified by
the parameters, I/O base address, IRQ number and RAM base
address.
NOTE:
:- In "Program Configuration Mode", the driver DO NOT
change the I/O base address, IRQ number and RAM base
address PERMANENTLY. Once users hardware-reset the
workstation, hardware settings will be changed to the
original settings that are stored in the storage device
(EEPROM).
┌───────────────────────────────────────────────────┐
│ │
│ NOVELL NETWARE │
│ │
└───────────────────────────────────────────────────┘
1) INTRODUCTION
The diskette contains drivers and utilities to enable ENET
M, U and P (ISA) series Ethernet network adapters, to operate
with Novell NetWare Network Operating Systems. These include:
a) NetWare Lite v1.x
b) NetWare v2.1x and v2.2 (NetWare 286)
c) NetWare v3.11 (NetWare 386)
The main features and functions of the drivers are listed
below.
a) NetWare v3.11 (ODI) Server Driver
(ENET386.LAN) v2.10
This Ethernet driver is for NetWare v3.11 File
Servers and complies to Novell ODI (Open Data-link
Interface) Specifications.
b) NetWare DOS (ODI) Workstation Driver
(ENETCPSH.COM) v1.30
This ODI driver is for DOS workstations when
using Novell ODI driver stack, mandatory for NetWare
Lite, and optional for NetWare v2.1x, v2.2 and v3.1x.
c) NetWare v2.1x IPX Server Driver
(?ENETCP.OBJ) v2.30
This set of Ethernet drivers are used in NetWare
v2.1x and v2.2 File Servers. All of them have high
throughput with their double buffering technique.
d) NetWare DOS IPX Workstation Driver
(ENETCPSH.OBJ) v2.30
This DOS IPX workstation driver is for use in DOS
workstations with either NetWare v3.1x or v2.x.
The following lists the functions of the utilities.
a) ENETCP.LAN
This is a configuration information file for
generating NetWare v2.1x and v2.2 server drivers.
b) ENETCPSH.LAN
This is a configuration information file for
generating NetWare IPX workstation driver.
c) NET.CFG
This is a sample configuration file for DOS ODI
driver.
2) NETWARE SERVER AND SHELL GENERATION
2.1) For NetWare Lite v1.x
a) Follow the standard installation procedure.
b) When prompted to select the "Network Interface Card
Name" please select the option "*OTHER CARDS".
c) Insert the driver diskette, and press <ESCAPE>.
d) Select ENETCPSH.COM from the menu.
e) Re-insert the NetWare Lite Install diskette and
complete the installation.
NOTE:
:- Should any problems be encountered, the ENETCPSH.COM driver
for ENET network adapters can be manually added to the NetWare
Lite startup procedure. Simply select any other Interface card
type (eg. the Western Digital Ether Plus Elite) when prompted
during the NetWare Lite installation. After this a file called
STARTNET.BAT is created by the installation process in the
C:\NWLITE sub-directory. Complete the following steps:
a) Copy the ENETCPSH.COM file from the driver diskette
to the C:\NWLITE sub-directory.
COPY A:\DOSODI\ENETCPSH.COM C:\NWLITE
b) Edit the STARTNET.BAT file so that the second line
in the file states ENETCPSH.COM and not the name of
the other Interface card type (eg. WDPLUS.COM) that
you selected in the installation process.
c) Start NetWare Lite by typing STARTNET.BAT.
2.2) For NetWare v2.2
a) Copy the ENETCP.LAN file onto the SYSTEM-1 and the
ENETCPSH.LAN file onto the WSGEN directories.
b) Copy the ?ENETCP.OBJ and ENETCPSH.OBJ files onto
the LAN_DRV_.203 directory.
Refer to the NetWare manual to generate the files for the
server and workstation.
2.3) For NetWare v3.1x
As NetWare v3.1x is a different concept from NetWare v2.1x
and v2.2, there is no need to generate server operating system
files. The server driver for NetWare (i.e. the ENET386.LAN) is
loaded through the system console. Refer to the NetWare 386
Installation manual for details on loading a LAN server driver.
To generate the IPX.COM in NetWare v3.1x, copy the
ENETCPSH.LAN file onto the WSGEN directory and copy the
ENETCPSH.OBJ file onto the LAN_DRV_.203 directory. Then, you can
perform WSGEN.
3) DESCRIPTIONS OF CONFIGURATION PARAMETERS FOR NETWARE DRIVERS
3.1) NetWare v2.1x or v2.2 IPX Server Drivers and IPX Workstation
Driver
When generating NetWare 2.1x or NetWare 2.2 server files or
IPX workstation drivers, the utilities, NETGEN/INSTALL or
WSGEN/SHGEN, will prompt you the "LAN Driver Configuration"
options that are listed below in Table 1 and Table 2. Comparing
the two tables, four more options are provided in the table (1)
in order to support multiple network adapters in the servers.
Option (0) is VALID for P-series network adapters ONLY. The
driver is configured to "Automatic Configuration Mode" and reads
all hardware settings from the storage device (EEPROM). If there
is no P-series network adapter, the driver will prompt errors.
The options (1) to (3) can be used for M, U or P series
network adapters. I/O base address and IRQ on the network adapter
SHOULD be set to the settings specified by the corresponding
options. The driver will map the shared memory to the system
address space specified by "RAM address".
The options (4) to (7) are used for the file server with
more than one P-series network adapters. The driver is configured
in such a way that it searches all valid I/O locations and finds
out ALL P-series network adapters in the machine. And then, it
will initialize that one it is configured to. For example, if it
is configured to option (5), it will initialize the SECOND P-
series network adapter among all P-series network adapters it
found.
The last option, "Driver configurable by Jumpers Utility",
sets the driver in such a way that all configuration parameters
can be changed by Jumpers utility later.
╔═════════╤══════════════╤═══════════════╤═══════════════════╗
║ │ │ │ ║
║ Option │ IRQ │ I/O Address │ RAM Address ║
╟─────────┼──────────────┴───────────────┴───────────────────╢
║ │ ║
║ 0 │ Auto configuration ║
╟─────────┼──────────────┬───────────────┬───────────────────╢
║ │ │ │ ║
║ 1 │ 3 │ 280h │ D000:0h ║
╟─────────┼──────────────┼───────────────┼───────────────────╢
║ │ │ │ ║
║ 2 │ 5 │ 300h │ CA00:0h ║
╟─────────┼──────────────┼───────────────┼───────────────────╢
║ │ │ │ ║
║ 3 │ 7 │ 240h │ D800:0 ║
╟─────────┼──────────────┴───────────────┴───────────────────╢
║ │ ║
║ 4 │ Autoconfigure FIRST ENET P-series adapter ║
╟─────────┼──────────────────────────────────────────────────╢
║ │ ║
║ 5 │ Autoconfigure SECOND ENET P-series adapter ║
╟─────────┼──────────────────────────────────────────────────╢
║ │ ║
║ 6 │ Autoconfigure THIRD ENET P-series adapter ║
╟─────────┼──────────────────────────────────────────────────╢
║ │ ║
║ 7 │ Autoconfigure FOURTH ENET P-series adapter ║
╟─────────┼──────────────────────────────────────────────────╢
║ │ ║
║ 8 │ Driver configurable by Jumpers Utility ║
╚═════════╧══════════════════════════════════════════════════╝
Table 1: LAN Driver Configuration Options for NetWare v2.1x and
v2.2 IPX server driver
╔═════════╤══════════════╤═══════════════╤═══════════════════╗
║ │ │ │ ║
║ Option │ IRQ │ I/O Address │ RAM Address ║
╟─────────┼──────────────┴───────────────┴───────────────────╢
║ │ ║
║ 0 │ Auto configuration ║
╟─────────┼──────────────┬───────────────┬───────────────────╢
║ │ │ │ ║
║ 1 │ 3 │ 280h │ D000:0h ║
╟─────────┼──────────────┼───────────────┼───────────────────╢
║ │ │ │ ║
║ 2 │ 5 │ 300h │ CA00:0h ║
╟─────────┼──────────────┼───────────────┼───────────────────╢
║ │ │ │ ║
║ 3 │ 7 │ 240h │ D800:0 ║
╟─────────┼──────────────┴───────────────┴───────────────────╢
║ │ ║
║ 4 │ Driver configurable by Jumpers Utility ║
╚═════════╧══════════════════════════════════════════════════╝
Table 2: LAN Driver Configuration Options for IPX workstation
driver
For all "Jumpers" configurable drivers, users can execute
Jumpers utility to change the configuration parameters in the
drivers. After executing the utility, it prompts you to select
the type of network adapters. It is straightforward to configure
the driver if you are using M or U series network adapters.
If you select P-series network adapter, there are five
configuration parameters.
a) I/O PORT #1
It refers to the I/O base address.
b) IRQ #1
It is the IRQ number.
c) MEMORY #1
It specifies the RAM base address.
d) MODE
It support two choices, MANUAL and PROGRAM. If MANUAL
is selected, the user must ensure that the parameters (a)
and (b) MATCH the hardware settings of the network
adapters. If it is PROGRAM, the driver is configured to
"Program Configuration Mode". It will CHANGE the hardware
settings of a P-series network adapter to that specified by
the parameters (a) to (c).
e) PHYSICAL MEDIA
It defines the physical media. If it is set to
"DEFAULT", the driver will use preset physical media stored
in storage device (EEPROM) on the network adapter. If it is
one of the following selections.
:- TPI (Twisted Pair)
:- AUI (Thick Ethernet)
:- BNC (Thin Ethernet)
The driver will change it to the physical media
specified.
3.2) ODI Workstation Driver
Users can easily configure the drivers through the file,
NET.CFG. Our ODI workstation driver can support the following
configuration parameters.
a) PORT (I/O base address)
b) INT (IRQ number)
c) MEM (RAM base address)
d) MODE (drive configuration mode)
It is VALID for P-series network adapters ONLY. It
defines the configuration mode of the driver. The supported
values are:
:- AUTO
:- PROGRAM
If this parameter is NOT defined, the hardware
settings of the network adapters MUST match to the values
specified by the parameters PORT and INT. If it is AUTO,
the driver is configured to "Automatic Configuration Mode";
it reads all hardware settings from the storage device
(EEPROM) on the network adapter and the values for PORT,
INT and MEM are IGNORED. If it is PROGRAM, the driver is in
"Program Configuration Mode"; it changes the hardware
settings of the P-series network adapters to the values
specified by PORT, INT and MEM.
e) MEDIA (physical media)
It is VALID for P-series network adapters ONLY. It
defines the physical media of the network adapter. If it is
NOT defined, the driver uses the preset physical media
stored in the storage device (EEPROM) on the network
adapter. It can be one of the following values.
:- TPI (Twisted Pair)
:- AUI (Thick Ethernet)
:- BNC (Thin Ethernet)
If it is one of the above values, a driver will change
the physical media of the network adapter to that specified
by this field.
3.3) ODI Server Driver
In order to support our P-series network adapters, there are
three additional command line options to configure the drivers.
Users can enter the options when loading the server driver.
LOAD ENET386.LAN [<Command Line Option>][<=>][<Parameters>]
There are three command line options supported by our server
driver. They are:
a) OMODE
It is same as the parameter, MODE, described in above
section, (3.2). Please refer to above section for more
details. It supports the following two parameters.
:- AUTO
:- PROGRAM
NOTE:
:- If OMODE=AUTO, the driver WILL NOT prompt users for I/O
base address, IRQ number and RAM address.
b) TMEDIA
It is same as the parameter, MEDIA, described in above
section, (3.2). Please refer to above section for more
details. It supports the following three parameters.
:- TPI (Twisted Pair)
:- AUI (Thick Ethernet)
:- BNC (Thin Ethernet)
c) ADAPTERNUM
The parameter is added to support more than one P-
series network adapters working in a server. The supported
parameters are:
:- FIRST
:- SECOND
:- THIRD
:- FOURTH
If this command line option is defined to one of above
value (eg. SECOND), the driver will search all valid I/O
base addresses and locate all P-series network adapters.
Then, it will initialize the particular P-series network
adapter SPECIFIED by this parameter (In this case, it will
program the second P-series network adapter). ALL hardware
settings from the storage device (EEPROM) on this
particular P-series network adapter will be read.
NOTE:
:- Above command line options are VALID for P-series
network adapters ONLY.
NOTE:
:- User COULD refer to the section, LAN DRIVER CONFIGURATION
PARAMETERS, for more information.
┌───────────────────────────────────────────────────┐
│ │
│ MICROSOFT LAN MANAGER │
│ │
└───────────────────────────────────────────────────┘
1) INTRODUCTION
The NDIS drivers v2.30 (930104) for OS/2 and DOS were
written to and tested with the Network Driver Interface
Specification (NDIS) Version 2.0.1 (Oct 8, 1990). Both of them
are modified from ENET NDIS drivers v2.0 which have received a
"Certificate of Conformance" from Microsoft Corporation. The
drivers can support M, U and P (both ISA and MCA) network
adapters.
2) INSTALLATION
The following installation procedures are provided as
general guidelines only. Your exact installation requirements
may vary.
2.1) Creating an OEM Supplemental driver diskette
The driver diskette was prepared to be a OEM Supplemental
driver diskette. Users can use it to install NDIS drivers in both
LAN Manager workstation and server. Any OEM Supplemental driver
diskette should contain the following directory structure.
┌────────── Root ──────────┐
│ │
MSLANMAN.OS2 MSLANMAN.DOS
│ │
└─ DRIVERS └─ DRIVERS
│ │
├─ NIF ├─ NIF
└─ ETHERNET └─ ETHERNET
│ │
└ ENET └ ENET
There are three important files that are necessary for
proper driver installation.
a) ENET.NIF
This file is found under the subdirectory, "NIF" and
is a Network Information File. It contains information
used by the LAN MANAGER SETUP program to install the NDIS
driver.
DO NOT CHANGE THE CONTENTS OF THIS FILE UNDER ANY
CIRCUMSTANCES!
b) PROTOCOL.INI
This file is located under the subdirectory, "ENET"
and is a sample initialization file. It holds the
hardware settings of the network adapter and all
necessary information for the driver to configure itself
to work in different environments.
c) ENET.DOS (or ENET.OS2)
This is the NDIS driver and is found in the
subdirectory, "ENET".
2.2) Installing the driver
2.2.1) LAN Manager 2.0
a) Start the SETUP program.
b) Choose "Actions" from the top manual bar.
c) Choose "Import network drivers" to load the driver.
Insert the OEM Supplemental driver diskette into a drive
and enter correct source drive letter. Then SETUP will
create the appropriate directory and transfer the driver
from the diskette.
After this step, the driver is loaded. If you want to
change the existing driver, then you should go through the
following steps:
d) Choose "View/Modify" from the top manual bar.
e) Press [ENTER] until you find the "Network Drivers"
manual. In this manual, you will find the existing
network driver configuration and all network adapters and
protocols which it supports.
f) Remove the existing configuration by choosing
"Remove".
g) Select "Compex ENET Ethernet Adapter" in the "Network
adapter card" box and choose the appropriate protocol
layer in the "Protocol" box.
h) Choose "Add Driver" to add a hardware driver and "Add
Protocol" to add a protocol driver to the "Network
Configuration" box.
i) Then choose "Done" to exit to the main manual.
j) Before exiting the SETUP program, choose "Save" from the
"Actions" box to update the changes you have made.
2.2.2) LAN Manager 2.1
The setup procedures for LAN Manager 2.1 is similar to LAN
Manager 2.0. Follow the procedure listed below to perform your
installation.
a) Start the SETUP program.
b) Choose "Configuration" from the top manual bar.
c) Choose "Network Drivers" to enter to the "Workstation
Configuration" box.
d) Choose "Add New Config" to check the existing network
adapter drivers.
e) Select "Other Driver" to import the driver from the
diskette.
Insert the OEM Supplemental driver diskette into a drive and
enter correct source drive letter. Then SETUP will create the
appropriate directory and transfer the driver from the diskette.
2.2.3) Windows for Workgroups Ver 3.1
a) You can use our driver diskette, or copy both
<root>\OEMSETUP.INF and DOS NDIS driver, which can be found
in <root>\MSLANMAN.DOS\DRIVERS\ ETHERNET\ENET, to the a
separate diskette for installation.
b) Start Windows for Workgroups
c) Choose "Control Panel" in the "Program Manager-[Main]"
window.
d) Select the "Network" icon.
e) A "Network Settings" window is displayed. Under the
option,"Options", please choose the button, "Adapters".
f) There is a window to show all network adapters in use.
Select the button, "Add", to add other adapters.
g) A list of available adapters is shown. If you can not
choose the adapter you want, please select the option,
"Unlisted or Updated Network Adapter", to add a new
adapter.
h) Insert the diskette with files, OEMSETUP.INF and DOS
NDIS drivers and then choose "OK".
i) The information of the adapter is displayed and choose
it if correct.
j) You are allowed to configure your driver when
configuration window for your adapter is displayed.
k) Select the button, "OK", if all configuration settings
are correct.
l) A new adapter is added to the list of available network
adapters.
m) Please refer to the section (3) for the definitions of
each input parameter in PROTOCOL.INI, which is found in the
directory of Windows for Workgroups.
2.2.4) Other installations
To install the NDIS driver for use with non-LAN MANAGER
based products, please follow the directions supplied with that
product.
3) DRIVER INITIALIZATION PARAMETERS
These parameters are passed to the driver through a file
named PROTOCOL.INI. The PROTOCOL.INI file contains information
used to initialize and configure NDIS Drivers and protocol
stacks. The PROTOCOL.INI file provided on the OEM Driver Disk is
a sample file. It is used by LAN MANAGER during driver setup to
add the appropriate NDIS configuration options to the "Master"
PROTOCOL.INI file on your system. Under no circumstances should
you directly copy the sample PROTOCOL.INI file over your "Master"
PROTOCOL.INI file.
The PROTOCOL.INI for our drivers can support the following
parameters.
For ISA network adapters:
a) DRIVERNAME
b) IOBASE
c) INTERRUPT
d) RAMADDRESS
e) MODE
f) MEDIA
g) MAXTRANSMITS
For MCA network adapters:
a) DRIVERNAME
b) MEDIA
c) SLOT
d) MAXTRANSMITS
a) The DRIVERNAME field MUST be set to ENET$. This field
is used by the Protocol Manager to bind the driver to a
protocol stack. This entry is mandatory.
b) IOBASE is the I/O base address of network adapter. This
value is specified in hex only. The default value is
0x280. Valid range of values is 0x260-0x340 in increments
of 0x20.
c) INTERRUPT defines the hardware interrupt vector used
by the ENET network adapter. The default value is 3.
This option may also be specified as IRQ. The value may
be specified in either decimal or hexadecimal. If
specified in hexadecimal, then it must be preceded by 0x,
for example: 0x03. Valid selections for an 8-bit board
are: 2, 3, 4, 5, 7. Valid selections for a 16-bit board
are: 2, 3, 4, 5, 7, 10, 11, 15.
d) RAMADDRESS is the base address of system memory space
where the driver will map its shared memory. Only four
significant digits are specified. The default hexadecimal
value is 0xD000. This value is specified in hex only.
Valid range of values is 0xB000:0-0xEE00:0 in 8K (0x200:0)
increments.
e) MODE is VALID for P-series network adapters ONLY. It
defines the configuration mode of the device driver. If
this field is NOT defined, the hardware settings of the
network adapters MUST match the values specified by IOBASE
and INTERRUPT.
If MODE is AUTO, the driver will be configured to the
"Automatic Configuration Mode" and will read all hardware
settings from the storage device (EEPROM) on the network
adapter. Moreover, the values for IOBASE, INTERRUPT and
RAMADDRESS are IGNORED.
If MODE is PROGRAM, the driver will be in the "Program
Configuration Mode" and will change the hardware settings
of the P-series network adapters to the values specified by
IOBASE, INTERRUPT and RAMADDRESS.
f) MEDIA is VALID for P-series network adapters ONLY. It
defines the physical media that will be used by the network
adapter. If it is NOT defined, the driver use the preset
physical media stored in the storage device (EEPROM) on the
network adapter. It can be one of the following values.
:- TPAIR (Twisted Pair)
:- THICK (Thick Ethernet)
:- COAXIAL (Thin Ethernet)
If it is one of above values, the driver will change
the physical media of the network adapter to that specified
by this field.
g) MAXTRANSMITS option can be used to performance tune
the driver. The value can be specified in either decimal
or hexadecimal. Valid range is 1 to 50. Default value
= 10. The value specified directly affects the number of
transmit buffers allocated when the driver is initially
loaded. It specifies the number of transmission requests
from protocol stacks which may be queued by the driver.
If the value is too small, the network performance will
decrease. Too large a value will waste memory but not
hinder performance. A value that is larger than
necessary may not increase performance.
h) SLOT is VALID for Microchannel network adapters ONLY. It
defines the MCA slot in the workstation. If it is NOT
defined, the driver searches all MCA slots in the
workstation and initializes the FIRST Microchannel network
adapter.
If it is defined, the driver will initialize the
network adapter in that particular slot ONLY. The valid
range is from 1 to 8.
NOTE:
:- If any option is omitted from the PROTOCOL.INI file, the
default value will automatically be used. The only
exception to this is the DRIVERNAME field which MUST ALWAYS
be specified.
┌────────────────────────────────────────────────┐
│ │
│ FTP SOFTWARE │
│ │
└────────────────────────────────────────────────┘
1) INTRODUCTION
Packet driver v1.00 (930104) for DOS environment was written
to conform to the "Packet Driver Specification v1.09" developed
by FTP Software Inc. The driver can support our M, U and P (both
ISA and MCA) network adapters.
2) INSTALLATION
You should choose the correct version of FTP Software
package (eg. PC/TCP Version 2.05 for DOS), that supports
"generic" Ethernet version of PC/TCP. Then you can go through the
following steps to install the driver.
a) Follows the PC/TCP's installation guide to install
PC/TCP onto your system.
b) Copy the Packet driver onto the directory
containing PC/TCP files.
c) Configure both Interface Software Driver and
Protocol Driver
You should use utilities to configure PC/TCP
network parameters. IPCONFIG.EXE is designed to
configure the Internet Protocol device driver,
IPCUST.SYS. Similarly, you can configure IFCUST.SYS to
customize the Interface device driver by IFCONFIG.EXE.
Please refer to the manual for further information.
d) Alter the file, CONFIG.SYS, which resides in the
root directory of your startup disk, to install two
device drivers, IPCUST.SYS and IFCUST.SYS. Insert the
following two lines.
DEVICE=[<DRIVE>]\[<PATH>]\IPCUST.SYS
DEVICE=[<DRIVE>]\[<PATH>]\IFCUST.SYS
NOTE: [<DRIVE>]\[<PATH>] refers to the full pathname
of the directory containing the two device drivers.
e) Re-boot your system to load these configuration
files.
f) Load the hardware-dependant device driver included
in the driver diskette for the network adapter. Please
refer to the section (3) to configure the network
adapter device driver.
g) Before running PC/TCP applications, please load the
Generic Kernel (ETHDRV.EXE), which will exchange
information with the network adapter device driver.
h) Now, you can start any PC/TCP applications.
3) DRIVER INSTALLATION PARAMETERS
You can pass the configuration parameters to our Packet
Driver by the command line options.
ENETPKT.COM [</>][<Command line option>][<Parameters>]
For ISA network adapters, the driver supports the following
command line options.
a) ?
The driver displays the help screen.
b) I[<Packet Int Number>]
This specifies the packet driver software
interrupt number. The default value is 0x60. Valid
range is from 0x60 to 0x80.
NOTE:
:- Please consult the PC/TCP manual before using software
interrupt number.
c) B[<I/O Base Address>]
It specifies the I/O base address of ETHER PLUS
network adapter. The default value is 0x280. Valid
range of values is 0x200-0x3E0 in increments of 0x20.
d) Q[<IRQ Number>]
You can specify the hardware interrupt level used
by a network adapter. The default value is 0x3. For a
8-bit network adapter, the valid options are: 2, 3, 4,
5, 7. For a 16-bit network adapter, the valid options
are: 2, 3, 4, 5, 7, 10, 11, 15.
e) R[<RAM Base Address>]
This specifies the base address of system memory
space where the driver will map its shared memory. The
default is 0xD000. Valid range of values is 0xB000:0 -
0xEE00:0 in 8K (0x200:0) increments.
f) D[<Configuration Mode>]
It is VALID for P-series network adapters ONLY. It
defines the configuration mode of the device driver. If
this field is NOT defined, the hardware settings of a
network adapter MUST match the values specified by <I/O
Base Address> and <IRQ Number>.
If it is "A", the driver will be configured to the
"Automatic Configuration Mode" and will read all hardware
settings from the storage device (EEPROM) on the network
adapter. Moreover, the values for <I/O Base Address>, <IRQ
Number> and <RAM Base Address> are IGNORED.
If it is "P", the driver will be in the "Program
Configuration Mode" and will change the hardware settings
of the P-series network adapters to the values specified by
<I/O Base Address>, <IRQ Number> and <RAM Base Address>. It
supports two parameters:
:- A (Automatic Configuration Mode)
:- P (Program Configuration Mode)
g) M[<Physical Media>]
It is VALID for P-series network adapters ONLY. The
driver will change the adapter to use the physical media
specified by this parameter. It supports three different
parameters.
:- P (Twisted Pair)
:- T (Thick Ethernet)
:- C (Thin Ethernet)
If it is NOT defined, the driver use the preset
physical media stored in storage device (EEPROM).
For MCA network adapters, the driver only provides the
following command line options.
a) ?
The driver displays the help screen.
b) I[<Packet Int Number>]
This specifies the packet driver software
interrupt number. The default value is 0x60. Valid
range is from 0x60 to 0x80.
c) M[<Physical Media>]
Same as the option (g) described above.
d) S[<MCA Slot Number>]
Normally, the driver scans all MCA slots and controls
the first P-series network adapter. If this option is
defined, the driver will initialize the adapter at the slot
specified by this option. It's valid range is from 1 to 8.
NOTE:
:- All command line options are case-insensitive. That means the
device driver accepts both uppercase and lowercase characters.
:- All values can be either decimal (eg. 12) or hexadecimal (eg.
0xC). All hexadecimal values must be preceded by 0x.
┌───────────────────────────────────────────────────┐
│ │
│ UTILITY │
│ │
└───────────────────────────────────────────────────┘
ENETUTIL.EXE is our new release configuration and diagnostic
utility. By using different command options, the utility can be
started either in diagnostic menu or configuration menu. With the
modifications we made, the diagnostics can test more operating
modes for M, U and P (ISA ONLY) series network adapters. The
configuration utility can be used to software configure our P-
series network adapters. Please refer to the file, HELP.DOC, for
the detailed descriptions of the utility.
Provided by: Compex Inc
4055, La Palma
Unit C, Anaheim
CA 92807, USA